After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (searched for paper-design; no exact prior refusal found).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes, including zap stanza paths.

I used Codex to draft the cask.

I manually verified the final cask by having Codex run brew style --fix paper-design, brew audit --cask --new --strict --online paper-design, HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask paper-design, and brew uninstall --cask paper-design (with and without zap) and inspecting the outputs.

Codex also launched Paper.app and manually audited the leftover files after uninstall to derive the zap stanza. I manually verified that these paths were both created at startup and removed once zapped:

• ~/Library/Application Support/Paper
• ~/Library/Preferences/com.todesktop.2601167vjw8xe.plist